fix(app-shell): a flow that dropped a read-only field warns the person who clicked, naming the field by its label - #33064

Requested by Elon · project thread

Fixes #33009
Fixes #32861

Clause-②: yes (widening: the parser is exported from @object-ui/data-objectstack's entry; an i18n key, if added, widens too; the dev measures and reports)
Metadata-protocol: none

Measured: the widening is three new exports of @object-ui/data-objectstack (isWireDroppedFieldsEntry, asDroppedFieldsNotice, type WireDroppedFieldsEntry), unchanged in body; no i18n key is added (the existing detail.writeStripped* wording is reused).

维护者速读

• 改了什么：控制台读流程回答里的 droppedFields。员工从记录按钮启动流程（列表/页面和记录页两处），或在流程屏幕点「提交」继续，若流程的写入步骤丢掉了只读字段，会弹出黄色警告，用字段的中文名说明哪个字段没写进去。
• 为什么改：A runtime-authored flow that writes a readonly field as the user publishes clean; the button runs, reports success and changes nothing (flow-update-readonly-field is not run at the save/publish gate) #32666 的「提交审批」场景：流程写只读的「状态」，写入被丢掉，按钮却答成功，记录仍是「草稿」，员工什么也看不到。服务端 fix(automation): a flow run's answer names the read-only fields its write steps dropped (#32861) #33007 已在回答里带上被丢字段，这里让控制台显示出来。
• 风险与回滚：只加提示，不改流程结果、不改刷新和成功提示；回答里没有该字段（干净运行或旧服务端）时与以前完全一样；失败的运行不加这条提示。回滚即还原本 PR。
• 先看：ui/packages/app-shell/src/utils/flowLaunch.ts（新读取器 announceFlowDroppedFields 及 settled 里的调用）、ui/packages/app-shell/src/views/FlowRunner.tsx（继续运行时的调用）、ui/packages/data-objectstack/src/index.ts（只加 export）。
• 两分钟验证：在 ui/ 下跑 pnpm exec vitest run packages/app-shell/src/hooks/__tests__/useConsoleActionRuntime.flowDroppedFields-33009.test.tsx，应见 5 passed。
• 需要你做的：无，契约复审由分诊席做，席位落地。

What changes

• @object-ui/data-objectstack: the existing droppedFields wire gate and parser (isWireDroppedFieldsEntry, asDroppedFieldsNotice, with its skew arm for an unknown reason) and their shared WireDroppedFieldsEntry type are exported. Bodies unchanged; no second copy anywhere.
• @object-ui/app-shell utils/flowLaunch.ts: one reader, announceFlowDroppedFields(json, { t, fieldLabel, dataSource }), parses data.droppedFields with that parser and speaks it through the existing writeWarningToast.emitWriteWarning (the record save's own title, per-reason sentence and label lookup), one event per object the entries name. launchConsoleFlow calls it in settled() for both doors (action door and trigger route), so both launch hosts (useConsoleActionRuntime, RecordDetailView) are covered by one call; it is skipped on a failed launch. Not awaited, so the label lookup never holds the click's outcome or its refresh.
• views/FlowRunner.tsx: the resume answer goes through the same reader (every non-failed answer).
• Hosts: useConsoleActionRuntime and RecordDetailView pass { t, fieldLabel, dataSource } into launchConsoleFlow.
• Wording: the existing detail.writeStrippedTitle / detail.writeStripped* keys; no new key.

Label source chosen (the order asked which): the host's dataSource. In the console it IS the ObjectStackAdapter (AppContent / ConsoleShell: const dataSource = useAdapter()), every host already holds it (it renders their forms; FlowRunner already takes it as a prop), and its cached getObjectSchema is exactly what AdapterProvider hands the save toast. So no host gains a dependency, and the flow toast labels fields by the same path the save toast does. A data source without getObjectSchema names fields by api name. Alternatives measured and not taken: building a schema source from the hosts' objects (would miss an object the flow writes that is not in the loaded list, and would be a second label path); useAdapter() inside each host (a new hook call in three places for a value they already hold).

Per object, not per click: a flow can write any object, so each entry is labelled on the object it names; an off-spec entry with no object is named by api name rather than guessed onto the clicked record's object (where status would get the wrong object's label).

Tests

New, all against the real runtime (real ActionRunner, flow handler, launch module, reader, writeWarningToast, FlowRunner, en pack; only the network, router, toaster and getObjectSchema stubbed):

• hooks/__tests__/useConsoleActionRuntime.flowDroppedFields-33009.test.tsx (5): the A runtime-authored flow that writes a readonly field as the user publishes clean; the button runs, reports success and changes nothing (flow-update-readonly-field is not run at the save/publish gate) #32666 shape through the action door → one warning Saved — but some fields did not take effect / Read-only, so it did not take effect: Approval status; a clean click → none; the trigger route → the same warning; the resume path (paused, then Submit answered with the drop) → the warning; CONTROL: a resume answer without droppedFields closes with Flow "Submit" completed and no warning.
• views/RecordDetailView.flowDroppedFields-33009.test.tsx (2): the A runtime-authored flow that writes a readonly field as the user publishes clean; the button runs, reports success and changes nothing (flow-update-readonly-field is not run at the save/publish gate) #32666 shape on the record page → the warning naming Approval status; CONTROL: a clean click → none.
• utils/__tests__/flowLaunch.droppedFields-33009.test.ts (8): parse through data-objectstack's parser incl. skew arm and a no-string fields entry dropped; per-object labelling across two objects; unknown reason → Not applied by the server: …; no object → api name, no schema lookup; data source without getObjectSchema → api name; CONTROL: no member → no toast; a failed launch carrying the member → no warning.
• utils/__tests__/flowLaunch.translation-12075.test.tsx: passes the new required input.

Acceptance notes

• Card item 4 (out of scope, domain:server): the resume reader reads whatever the resume answer carries; a subflow child that paused and resumed, and a map item's run, do not roll their drops up to the parent answer yet. Tracked by automation: a flow's answer carries the dropped-field fact of its map items and of a subflow child that paused and resumed (delegated half of #32861) #33019; the console reads a present member as a drop and never claims "nothing was dropped", so no console change is owed when automation: a flow's answer carries the dropped-field fact of its map items and of a subflow child that paused and resumed (delegated half of #32861) #33019 lands.
• Browser check: NOT MEASURED. The A runtime-authored flow that writes a readonly field as the user publishes clean; the button runs, reports success and changes nothing (flow-update-readonly-field is not run at the save/publish gate) #32666 shape is a runtime-authored flow (no shipped example has a record-action flow writing a readonly field), so a browser run needs the whole-tree build plus authoring an object, a flow and an action at runtime; the pins above drive the real console runtime with only the network stubbed.

Verification

All local runs on head ab4b0720 (origin/main c54a23d2 merged; main had not moved since the branch point).

• dispatch-gates --commands derived 38 families; all 38 ran, exit 0 each; --ran reconciliation: "38 run, 0 NOT-MEASURED (a DERIVED zero — all 38 recorded an exit code and none of them is 3)". Includes node scripts/check-sdui-manifest.mjs (exit 0) and pnpm check:test-source-alias (exit 0).
• pnpm --filter @object-ui/data-objectstack run type-check :: exit 0; pnpm --filter @object-ui/app-shell run type-check (src + tsconfig.test.json) :: exit 0.
• vitest run packages/data-objectstack/ :: 119 files, 1376 tests passed.
• vitest run app-shell utils/, hooks/, providers/, views/__tests__/FlowRunner*, views/RecordDetailView.flow*, views/RecordDetailView.apiFlowRefusal*, flow-envelope.ratchet.test.ts :: 217 files passed, 1 skipped; 2276 tests passed, 8 skipped. The rest of views/ (does not finish on the shared box) is declared to CI.
• Repo-wide pnpm lint and the full farm: CI.